An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi guys We have tried to push our app live for over a month now, and there is total radio-silence from apple. Trying to call the Danish/Irish number, no one picks up the phone - we have tried several times and it just keeps playing waiting tone for hours. We have tried writing, but nothing gets back. From may 12th, we got a response on may 28th to update a few things in the app. That was done and then resubmitted. Then again on June 3rd. But from june 3rd, radio silence until june 15th. And now, again radio silence from 15th. We have clients who are waiting for the app, and all of our income relys on this. But no response. I was expecting more from one of the worlds biggest companies.

Hi everyone,  I'm a relatively new developer and I just received my first App Store rejection. I'm posting here because I'm genuinely stuck and hoping the community can help me figure out where to even begin.  The Problem:  My app was rejected under Guideline 5.6 - Developer Code of Conduct - Review Suspended. The full message is the standard one: the app doesn't meet the "required quality standard," it's "not eligible for resubmission," and I should "ensure every screen, interaction, and piece of content has been thoughtfully designed" before submitting a new app.  Here's why I'm confused:  The rejection came with ZERO attachments. No screenshots. No screen recordings. No crash logs. No specific mention of a buggy feature, a broken button, or an unfinished screen. It's just a blanket statement about "quality" and "polish."  in my case, there's absolutely nothing to go on.  What I've checked so far:  I've tested the app on multiple physical devices (iPhone 12, 14, 15) – no crashes. I've reviewed every screen for placeholder text, "Lorem Ipsum," or dummy images – none found. I've checked the In-App Purchase / subscription screen for proper legal disclaimers and auto-renewal text – all present. I've made sure there are no debug logs or test toggles left in the production build. Everything looks fine to me, which is why I'm so lost. Without specific feedback, I don't know if the issue is:  A UI inconsistency I'm blind to? A subtle crash that only happens on a device I don't own? An issue with the paywall flow that I've misunderstood? Something about the metadata, screenshots, or app description? My questions for the community:  Has anyone else received a Guideline 5.6 rejection with no attachments? Is this common, or does it suggest the reviewer flagged the app as "low-quality" purely based on first impressions (like the design feels outdated or the concept is too simple)? Since the message says replies and resubmissions of this binary won't be reviewed, and I can't get clarification from the reviewer, what's the safest way to proceed? Should I:  Create a completely new App ID and submit as a new app? Or can I submit a new version under the same App ID? (I've heard mixed answers on this.) More importantly – how do I figure out what to fix? Without a starting point, I'm worried I'll fix the wrong things and get rejected again, which I know can lead to account termination after repeated violations. Are there any "hidden" quality checks that reviewers apply that aren't obvious to developers? For example, does Apple penalize apps that:  Have a generic icon or unpolished splash screen? Take too long to load on first launch? Have unclear navigation or confusing user flow? Lack a proper onboarding/tutorial for first-time users?   Thanks in advance for any help you can offer. I really want to get this right and not waste my one or two remaining chances. my app id : 6764726742

Hi everyone, I'm hoping someone from Apple or a senior community member can help escalate my situation. About four weeks ago, I received a termination warning on my developer account related to an app called Checklist Buddy (originally named Cessna Checklist Buddy). I renamed it after realizing I didn't have formal written permission from Textron Aviation, even though I had verbal approval. I believe that name change — or possibly code similarity between apps — may have triggered a flag. I have three apps on the store: WIB 26, Checklist Buddy, and Pure International 2026. WIB 26 is live and functioning fine. Pure International 2026 is the critical one — it's an event app for a pageant happening next week and delegates are counting on it. I have submitted multiple appeals and tickets over the past four weeks with zero acknowledgment from Apple. Last week I called Apple Support and spoke with a representative. He pulled up my account and confirmed there were notes showing an appeal on file, but no reason whatsoever was documented for the termination warning — even he couldn't see why. He escalated my case to a senior advisor and told me I would hear back within 3 business days. It has now been 7 days with no contact. I understand Apple has a high volume of cases, but this is affecting my livelihood. I have a real event with real attendees next week who need this app, and I cannot distribute it or push updates because my account is in a restricted state pending this appeal. If any Apple staff reads this — my case has been escalated to the senior advisor team and is sitting in an email queue. I just need a resolution or at minimum a reason for the original warning so I can address it properly. Any advice or help from the community is also appreciated. Thank you.

Hi everyone, Our app has been in “Waiting for Review” status for 7 days. There are no outstanding actions, messages, or compliance issues shown in App Store Connect. Has anyone experienced similar review delays recently? If so, how long did it take for the review to begin? App ID: 6759098797 Submission ID d6c075db-883c-44fe-8220-005de5a2ed1e Thanks in advance for any guidance.

Hi, Was there an issue or something with the recent App Review queue? Since our app has been in "Waiting for Review" status for about 1 week and got nothing from the review team. App ID: 6759098797 Submission ID: d6c075db-883c-44fe-8220-005de5a2ed1e I'm wondering if we could get any support or help here by posting the issue.

Hello everyone, We have a SaaS product and are currently transitioning our business model. Previously, we used a standard recurring subscription model implemented via StoreKit 2 in our iOS app. Recently, we changed our pricing to a performance-based model, where we charge a percentage fee based on the user's specific usage and performance. On our web platform, we use Stripe to calculate and accept these dynamic percentage-based payments. I have two questions regarding this transition for our iOS app: Payment Gateway: Since our new pricing model is a variable, performance-based percentage rather than a fixed subscription, does Apple allow us to integrate Stripe directly into the iOS app to process these payments? The service provided is digital. Removing Old Subscriptions: We have completely commented out all StoreKit code in our app build since we are no longer offering those plans. However, we cannot find a "Delete" option in App Store Connect to remove the old subscription items. What is the proper way to completely remove these from our app's backend and store listing? Any guidance on the best way to handle this transition and remain compliant with App Review would be greatly appreciated. Thank you!

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hello, I'm developing a Capacitor/Next.js iOS app with RevenueCat for auto-renewable subscriptions. On a real iPhone via TestFlight, StoreKit never returns my subscription products, so the Apple payment sheet never appears. App TestFlight builds tested: 110, 111, 112 (iOS 1.1.0) In-App Purchase capability enabled on App ID Paid Applications Agreement: active Banking/tax: active Subscription product IDs (auto-renewable, same subscription group) vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro (exit offer) What happens Install app from TestFlight on physical iPhone Navigate to paywall App calls RevenueCat → Purchases.getProducts() with the 3 product IDs above StoreKit returns 0 products (or configure/getProducts times out) UI shows: "Apple Store: 0 subscriptions on this device — Sandbox popup cannot open" Tapping subscribe does not open the Apple payment sheet Fallback prices appear (3.49 / 29.99) instead of live App Store prices (3,49 € / 29,99 €), which suggests StoreKit is not returning products. What we already verified Correct bundle ID in build metadata NEXT_PUBLIC_REVENUECAT_API_KEY_IOS (appl_*) embedded in EAS production build Provisioning profile regenerated and active Subscription metadata corrected (was Rejected, now Waiting for Review) All 3 subscriptions attached to app version submission RevenueCat offering "default" with monthly, annual, and annual_intro packages App Store Server Notifications URL configured to RevenueCat Legal pages open in-app (no external cookie banner on native) Testing on TestFlight only (not Safari/web) App Review context We received Guideline 2.1(b) rejections because: Error on purchase page Exit offer (50% OFF / €1.91 per month equivalent) referenced product vytalai_premium_yearly_intro which was not submitted for review initially — now added and submitted with the app version. Question Even with subscriptions in "Waiting for Review" state and metadata completed, should StoreKit Sandbox/TestFlight return these products on device so we can test the payment sheet before approval? If not, what exact App Store Connect state is required for StoreKit to return products on TestFlight? Any guidance on why getProducts would return 0 for valid product IDs on a TestFlight build would be greatly appreciated. Thank you.

Hi everyone, I'm hoping someone from App Review (or anyone who's been through this) can help, because I'm a bit stuck. My app Mingle (Apple ID: 6770285096, Version 1.0.1) has been sitting in "Waiting for Review" for well over a week now. I first submitted at the start of June, and after it sat there for ~6 days with no movement at all, I figured something might be wrong, so I canceled and resubmitted. The new one has now been waiting since June 15 with the same silence: Submission ID: c919ad21-902a-4a3c-a6cc-a5fbd9f7e2b1 Every previous review of this app went through in under 48 hours, so this is really out of the ordinary. I've already opened a support request through Contact Us, but I haven't heard anything back yet. This is genuinely blocking me - I've been trying to get this release out since the beginning of the month and everything on my end is ready and waiting on the review. Is there anything I can do to move this along, or any reason a submission would get stuck like this? If anyone from App Review could take a look, or point me to the right channel, I'd really appreciate it.

Our app submission has been in "Waiting for Review" status for 8 days after another 8 days before that with no review. Typical review time is 24–48 hours, so this appears to be stuck. We have not received any communication from App Review during this period and there are no outstanding items in App Store Connect. Could a member of the App Review team please check the status of this submission? App Name: Blingz App ID: 6759068218 Bundle ID: com.apperfun.hub Version: 1.39.1 Submission ID: 381c3dce-68f5-426b-b6de-807f513d370f Submission Date: Jun 13, 2026 Support Case ID: 102915835489 Thank you.

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

Hello, I am reaching out regarding a critical review delay affecting Summer Rockz (App ID: 6763247379), a European festival discovery app. Version 2.0.0 has been in "Waiting for Review" since June 16, 2026 at 17:30 CET with no movement. Review history for v2.0.0: June 3 — Submitted for review June 4 — Rejected (Guideline 1.1) June 4 — Addressed and resubmitted same day June 16 — Rejected again (Guideline 1.1) June 16, 17:30 — All issues addressed and resubmitted Today, June 19 — Still "Waiting for Review", 3 days with no status change What I have already done: Submitted an Expedited Review request with a documented business justification (summer festival season, time-critical launch window) Opened multiple support tickets Responded in detail to both rejection notices via the Resolution Center Why this is urgent: Summer Rockz serves a seasonal audience tied to the European festival calendar. June and July are the peak months. Every day of delay directly impacts active users and partner festivals that depend on the app being live. The app has no unresolved guideline issues. Both rejection points were addressed immediately and documented in the Resolution Center. Could someone from the App Review team investigate whether this submission is stuck or flagged? I am not asking to bypass the process — I am asking for visibility on a submission that appears frozen with no review activity after 3 days. Thank you.

Hello, I am the developer of Kodogram, an educational programming platform that allows users to learn, inspect, edit, and execute code. My app was rejected twice under Guideline 2.5.2 despite the fact that all executable source code is fully visible and editable by users before execution. According to Guideline 2.5.2, educational apps may download code provided that: The code is used solely for educational purposes. The source code is completely viewable by the user. The source code is editable by the user. Kodogram is designed specifically for programming education. Users can learn, inspect, edit, share, fork, and test source code written in multiple programming languages, including HTML, CSS, JavaScript, Python, C, C++, C#, Java, PHP, and others. In the application: Users can view the complete source code before execution. Users can edit the source code before execution. Users can create forks of shared projects and modify them. Users can test and learn code written in multiple programming languages. Code execution occurs only after the user has reviewed and optionally modified the source code. During the review process, Apple attached a screenshot showing only the final "Run Output" screen. In response, I provided additional screenshots demonstrating: Complete source code visibility before execution. Separate source code views for HTML, CSS, and JavaScript examples. The code preview/editor screen where users can review and modify code. The final output screen shown only after the code has been reviewed and executed. The attached screenshots use HTML, CSS, and JavaScript as examples, but the same workflow applies to all supported programming languages within the platform. My question is: Has anyone experienced a similar Guideline 2.5.2 rejection for an educational coding application where the source code was already fully visible and editable before execution? Is there any additional requirement, documentation, or implementation detail that App Review may expect beyond demonstrating that source code is completely viewable and editable by the user prior to execution? Any guidance or shared experiences would be greatly appreciated. Thank you.

大家好， 想请教一下是否有开发者遇到过类似情况，并愿意分享处理经验。 假设某 App 收到第三方发起的知识产权投诉（例如图片、字体、素材等相关内容）。 开发者收到投诉后已经： 完成内部核查； 删除或替换了被投诉内容； 发布整改版本； 当前 App 及相关线上服务中已无法访问被投诉内容。 但投诉方认为双方争议并未解决，并持续基于历史使用行为提出异议或再次发起投诉。 想了解大家是否遇到过类似情况： 开发者完成整改后，Apple 是否曾针对同一事项再次联系过你们？ Apple 是否要求过额外材料，例如整改说明、授权证明或其他补充文件？ 如果当前版本和线上服务已经无法访问被投诉内容，Apple 在后续处理中通常更关注哪些方面？ 有没有开发者遇到过已经完成整改，但仍然因为同一事项被进一步处理甚至下架的情况？ 对于这类已经完成整改、但双方仍存在历史争议的问题，Apple 后续通常是如何处理的？ 我理解每个案件情况不同，也理解 Apple 会根据个案进行评估。 这里只是希望了解其他开发者的实际处理经验，以便更好地理解 App Store 在知识产权投诉方面的一般处理方式。 感谢大家分享经验。

Hello App Review team - My app(App ID: 6756242440) is stuck in 'Waiting for review'. Once in a while updates are getting stuck like this, while other times same app reviews go through in 48 hours. Please help us understand any reasoning behind this so we can plan our development accordingly. Thanks in advance!

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

Hello everyone, I'm looking for advice because my first iOS app has been stuck in "Waiting for Review" since May 29. The app has never entered the "In Review" stage and the status has not changed for weeks. I have already contacted Apple Developer Support multiple times, and they keep telling me that everything looks normal and that I just need to wait. However, it has now been almost a month, which seems highly unusual compared to the review times other developers are reporting. Some details: First app submission Status: Waiting for Review Submitted on May 29 No messages in Resolution Center No rejection or request for additional information Apple Support says there are no issues with the submission Has anyone experienced a similar delay for a first app release? Did the review eventually start on its own, or was there something specific that had to be done? Any advice would be greatly appreciated. Thank you.

Hello everyone, I’m reaching out for some guidance regarding App Store Guideline 3.1.3(c) and an issue we’re facing during the app review process. Here’s the situation: Our app is designed exclusively for organizations (e.g., businesses, schools, etc.) and is not intended for individual users, consumers, or families. Organizations purchase access to our services directly through our website, and we manually onboard them into the app. Individual users cannot register themselves or gain access to the app unless they are part of a pre-approved organization. However, during the app review process, we received the following feedback: We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase. We believe this is a misunderstanding because: Our app does not allow individual users or families to register or access the app. All purchases are made outside the App Store via our website, and only organizations can complete these transactions. We manually onboard organizations and their users – there is no way for individuals to sign up or pay for access within the app. We’ve already explained this to the App Review team in App Store Connect, but we’re still facing issues. Has anyone else experienced something similar? If so, how did you resolve it? Here’s what we’ve done so far: Clearly stated in the app description that the app is for organizations only. Ensured that individual users cannot register or pay for access within the app. We’d appreciate any advice or insights from the community on how to better communicate this to the App Review team or if there’s something we might be missing. Thank you in advance for your help! Best regards, Bashar

Hello, I don't understand why Apple states that app reviews typically take 48 hours. In my experience, it has never been completed within 48 hours. It is usually at least 6–7 days, and in some cases I have waited up to two weeks just to receive a response. Another issue is that they never seem to provide all the problems clearly at once. I wait for a response, they point out one issue, I fix it, then after another week or two they identify a different issue that was already present from the beginning. This makes the entire process extremely slow and frustrating. Is there any way to get a faster response from the review team? Has anyone else experienced similar issues with App Review? Thank you.

Hello, My app has been in “Waiting for Review” status since May 28. App ID: 1471317275 The app was transferred to my developer account about two months ago. Since the transfer, previous reviews were completed without any issue, and I have not received any message in the Resolution Center or any indication that something is wrong with this submission. I am not sure if the app transfer could have affected the review queue, but the current submission has now been waiting for an unusually long time. Could someone from Apple please advise what I should do in this situation? Should I continue waiting, contact App Review Support directly, or resubmit the build? Thank you for your help.